home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Software Vault: The Gold Collection
/
Software Vault - The Gold Collection (American Databankers) (1993).ISO
/
cdr28
/
doc_proc.zip
/
SAMP-DOC.ZIP
/
MAIL.DOC
< prev
next >
Wrap
Text File
|
1992-11-16
|
41KB
|
505 lines
*************************************
* *
* M A I L *
* ON THE MVS/XA OPERATING SYSTEM *
* *
*************************************
John S. Ward
02/15/93
EJECT
The transmission of data among users on the AMDAHL 5860 (System D)
is possible through the use of TSO/E's Interactive Data Transmission
Facility. This facility provides a TRANSMIT command to send messages
and/or data sets to other users and a RECEIVE command to receive them.
An activity log of messages and data sets transmitted and received is
maintained under each userid. Nicknames and distribution lists can be
established for your convenience. Userid verification is performed
when you attempt to send mail to a userid on System D, and users are
notified when they have mail waiting. For information on how to use
this facility to send messages and/or data sets to users connected
to the BITNET network, read the handout on BITNET. For a complete
description of this facility, refer to the TSO/E COMMAND LANGUAGE
REFERENCE MANUAL - SC28-1134.
TRANSMIT command
The TRANSMIT command is used to send information from one user to
another. This command allows the sending of messages, data sets, or
data sets prefixed with messages. You may send partitioned data sets,
a member or members of a partitioned data set, or a sequential data
set. You cannot send data sets with keys or user labels, ISAM data
sets, or VSAM data sets. If you want to send a message, issue
TRANSMIT node.userid without any options. You will be prompted with
a screen to type in your message. When you are finished typing in
your message, press the PF3 key. You may terminate TRANSMIT by
pressing the PA1 key. If you want to send a data set prefixed with
a message, type the command "TRANSMIT node.userid MSG DATASET(dsname)".
You will be prompted with a screen to type in the accompanying message.
If you attempt to TRANSMIT to a nonexistent userid on the AMDAHL,
the TRANSMIT command is terminated and the following message is sent
to the terminal:
INMX151I TRANSMIT TERMINATED DUE TO INVALID USERID userid
If you send mail to a valid userid on the AMDAHL, the following
message is sent to the recepient:
+GSU001 MAIL WAITING FROM nodename/userid
This message appears when the recepient logs on if not logged on when
the message is sent or when the recepient hits return if already
logged on.
EJECT
The format of the TRANSMIT command is:
TRANSMIT nodename.userid DATASET(dsname) options
where
nodename is the name given to an institution's computer.
GSU's AMDAHL running MVS/XA (System D) is GSUMVS1.
userid is the userid of the person you are trying to
TRANSMIT to.
dsname is the name of the data set you wish to send. Enclose
a fully qualified name in quotes. This data set may
be a partitioned data set, a member or members of
a partitioned data set, or a sequential data set.
You cannot send data sets with keys or user labels,
ISAM data sets, or VSAM data sets.
options some frequently used options are described below.
To send a message or data set to more than one user at the same
time, enclose the list of names in parentheses as shown below:
TRANSMIT (nodename.userid nodename.userid ...) DATASET(dsname)
or establish a nickname and distribution list using the data set
NAMES.TEXT.
You may issue the TRANSMIT command from the COMMAND line or OPTION
line of any ISPF screen by prefixing the command with "TSO" as shown
below.
COMMAND => TSO TRANSMIT nodename.userid DATASET(dsname)
The TRANSMIT command has several options. A few of the more
frequently used options are described below. You may issue the TSO
command "HELP TRANSMIT" for more information, or refer to the TSO/E
COMMAND LANGUAGE REFERENCE MANUAL - SC28-1134 for a complete
description.
DATASET(dsname) - specifies the name of the data set to be
transmitted. If this option is not chosen,
TRANSMIT will assume you wish to send a
message and will prompt you for the
message.
MSG - specifies that a message is to accompany a
transmitted data set.
COPYLIST - COPYLIST specifies that a list of the
NOCOPYLIST specified addressees be built and placed as
a prefix to the message being sent or as an
accompanying message if a data set is being
sent. NOCOPYLIST is the default.
EJECT
EPILOG - EPILOG specifies that epilog lines con-
NOEPILOG tained in the NAMES data set be appended to
the message being sent. EPILOG is the
default.
PROLOG - PROLOG specifies that prolog lines con-
NOPROLOG tained in the NAMES data set be prefixed to
to the message being sent. PROLOG is the
default.
NOTIFY - NOTIFY specifies that the sender be not-
NOTIFY(ALL) ified when the data is received.
NONOTIFY NOTIFY(ALL) specifies that the sender be
notified when the data has been received by
all addressees. NOTIFY(ALL) overrides the
:NOTIFY or :NONOTIFY tag in the nickname
section of the NAMES data set. NOTIFY is
the default. To be sure that you are
notified when every addressee has received
the data, use NOTIFY(ALL).
PDS - PDS specifies that a member or members of a
SEQUENTIAL partitioned data set be unloaded before
transmission. Directory information is
preserved, but the receiver is forced to
restore the member(s) into a PDS.
SEQUENTIAL specifies that a member of a
partitioned data set or a sequential data
set be sent as a sequential data set.
Directory information is not preserved, but
the receiver can restore the data set as
either a sequential data set or a
partitioned data set. PDS is the default.
MEMBERS(list) - specifies a list of members to be trans-
mitted from the specified partitioned data
set.
LOG - LOG specifies that the transmission be
LOG(ALL) recorded in the LOG data set. LOG(ALL)
NOLOG will create a log entry for each addressee.
LOG(ALL) overrides NOLOG/NOLOGLST tags in
the NAMES data set. LOG is the default.
RECEIVE command
The RECEIVE command is used to receive information that has been
sent to you from another user. If you have mail waiting to be
received, the following message will appear when you logon or when you
hit return if you are logged on when the mail comes in:
+GSU001 MAIL WAITING FROM nodename/userid
EJECT
The format of the RECEIVE command is:
RECEIVE
NOTE: You may issue the RECEIVE command from the COMMAND line or
OPTION line of any ISPF screen by prefixing the command with
"TSO" as shown below.
COMMAND => TSO RECEIVE
If an interactive message has been sent to you it will be
displayed on the screen. You cannot specify a data set to save the
message to when you receive it, but a copy of the message is placed in
the LOG data set.
If an error-free data set has been sent, the following messages
will be displayed when you issue the RECEIVE command (any attached
message sent along with the data set would appear first):
INMR901I Data set 'dsname' from 'userid' on 'nodename'.
INMR906A Enter RESTORE parameters or 'DELETE' or 'END'. +
You may respond with a ? whenever you see a + to get more information
about what to do. If you entered a ? now, you would see:
INMR908A The input file attributes are: DISORG=_______,RECFM=__,
BLKSIZE=____,LRECL=_____,FILE SIZE = ____ +
If you again entered a ?, you would see:
INMR909A You may enter DSNAME, SPACE, UNIT, VOL, OLD/NEW, or
RESTORE/COPY/DELETE/END
If you enter END, the RECEIVE command will terminate leaving
the file on the spool to be received at a later time. If you
enter DELETE, the file will be erased from the spool. If you
simply press return at this point, the received data set will be
saved in the default data set name. The default is the same name
as the transmitted data set with the high level qualifier changed to
your userid. If you do not want the data set saved to this default
name, use the DSNAME option to specify the name of the data set to
use. The format is DSNAME('dsname') where dsname can be the name of a
new or existing data set. Put a fully qualified name in quotes. If
the data set already exists and its file attributes do not match those
of the incoming file, the RECEIVE command will terminate leaving the
file on the spool to be received at a later time. You may specify the
allocation parameters for a new data set or just use the defaults.
The default allocation parameters are given on the next page.
EJECT
PARAMETER DEFAULT VALUE
DSNAME If the data set was error-free, the default is the
same name as the transmitted data set with the high
level qualifier changed to your userid. When you
try to RECEIVE data sets containing errors, the
default is your_userid.RECEIVE.INVALID.FILE.
SPACE
primary default value for primary space allocation is a
size equal to the incoming data
secondary default value is 2.5% of the primary allocation
TRACKS or space to be allocated in TRACKS, CYLINDERS, or
CYLINDERS or BLOCKS. Default is TRACKS.
BLOCKS
DIRECTORY this option is only applicable when receiving into
a new partitioned data set. The default value for
directory blocks when receiving a sequential data
set into a new pds is 27. The default when
receiving a pds into a pds is the number of blocks
required for the received members.
NEW or If a value is not given for SPACE, The data set
OLD or disposition default is OLD. If that fails, NEW
MOD or is used and SPACE values are added.
SHR
If you attempt to restore the received data set to a data set that
already exists, you will be prompted with the message:
INMR045I Data set 'dsname' already exists. Reply 'R'
to replace it. +
Any response other than 'R' will terminate RECEIVE leaving the data
set on the spool to be received at a later time.
If you have successfully restored the received data set, you will
see the messages below:
INMR001I Restore successful to data set 'dsname'.
INMR900I ----------------------------------------
If you have any more data sets or messages to receive, they will
appear at this point. If you have no more messages or data sets
to receive, you will see the message:
INME000I No more Interactive Data Transmission Facility files are
available for the RECEIVE command to process.
EJECT
When you RECEIVE a data set containing errors, you will see the
following messages:
INMR921I Received file appears not to be an Interactive Data Transmissio
Facility file. The first record is: * first record appears her
INMR901I Dataset X.RECEIVE.INVALID.FILE from ? on ?
INMR907A Enter COPY parameters or 'DELETE' or 'END.'+
If you press the return key at this point, the data set will be
copied into the default data set 'your_userid.RECEIVE.INVALID.FILE'.
If there is already something in 'your_userid.RECEIVE.INVALID.FILE',
you will be prompted for permission to overwrite it:
INMR045I Data set 'RECEIVE.INVALID.FILE' already exists. Reply 'R'
to replace it. +
If you do not want the received file saved in the default file, do
not press return when prompted to enter copy parameters. Instead, use
the "DSNAME" option to specify the name of the data set to use. If
the file attributes of this data set do not match those of the file
you are attempting to receive, RECEIVE will terminate leaving the file
on the spool to be received at a later time.
For more information on the RECEIVE command, you may issue the
TSO command "HELP RECEIVE" or refer to the TSO/E COMMAND LANGUAGE
REFERENCE MANUAL - SC28-1134.
ACTIVITY LOG OF TRANSMIT AND RECEIVE
The TRANSMIT and RECEIVE commands will ordinarily log every
message and file transmitted and received to the data set
your_userid.LOG1.LOGSET. The entire text of any message transmitted
or received will be stored in this data set, but only the name of the
data set transmitted or received will be stored in the log. The NOLOG
option on the TRANSMIT command will cause the transmitted message or
data set name not to be logged to this log data set.
You can specify the name of the log data set through the :LOGNAME
tag in the control section or in nickname definitions of the NAMES
data set. You can have more than one log data set, but they must all
have the DCB attributes LRECL=255, BLKSIZE=3120, and RECFM=VB.
NICKNAME AND DISTRIBUTION LISTS
A user can define up to 10 data sets which contain synonyms for
node.userid and distribution lists. The name of the primary NAMES
data set must be your_userid.NAMES.TEXT. This data set will
contain the names of any other NAMES data sets.
EJECT
The NAMES data set is composed of two sections -- the control
section and the nicknames section. The control section comes first
and ends with the first :nick tag. The control section can contain
tags specifying names of other NAMES data sets, epilog and prolog
lines to be appended to all transmitted messages, and names of other
LOG data sets. There are no required tags for the control section.
The only defaults if not otherwise specified in the control section
are :LOG and :NOTIFY.
The nicknames section consists of nickname entries which begin
with the :NICK tag. The nicknames section includes tags specifying
nicknames for userid, the node name that the userid is on, text names
and addresses associated with each nickname, and distribution lists.
The only required tags in the nicknames section are :NICK, :USERID,
and :NODE.
All tags have the format:
:tagname.operand
Note: The : preceeding the tag name and the "." following the tag name
are required.
The control section may contain any or all (or none) of the
following tags:
:ALTCTL.dsname
This tag specifies the fully qualified name of another
data set to use in looking up nicknames. There can be
up to a maximum of ten :ALTCTL tags. TRANSMIT will
scan the data sets in the order listed. Control section
tags in these secondary NAMES data sets are ignored.
:EPILOG.text
This tag specifies a line of text to be appended to the
end of any transmitted message. The maximum length of
the epilog line is 72 characters and there can be up
to ten :EPILOG lines. These lines will be appended in
the same order as they are in the data set. The NOEPILOG
option of the TRANSMIT command will cause these epilog
lines not to be appended to the current message.
:PROLOG.text
This tag specifies a line of text to be prefixed to the
beginning of any transmitted message. The maximum length
of the prolog line is 72 characters and there can be up to
ten :PROLOG lines. These lines will be prefixed in the
same order as they are in the data set. The NOPROLOG
option of the TRANSMIT command will cause these prolog
lines not to be prefixed to the current message.
EJECT
:LOGNAME.dsname
This tag specifies the default qualifier for the log data
set name. If :LOGNAME is specified in a nickname entry,
that entry overrides the default entry in the control
section.
:LOG or :NOLOG
This tag controls the logging of entries into the log file
for addressees specified by node.userid in the TRANSMIT
command and for nicknames which do not specify a :LOG or
:NOLOG. A :LOG or :NOLOG tag specified in the nicknames
section will override the default set in the control
section. The LOG, LOG(ALL) or NOLOG option on the TRANSMIT
command overrides any default in the NAMES data set.
:NOTIFY or :NONOTIFY
This tag controls the notification that the addresses
specified by node.userid and the nicknames without a
:NOTIFY or :NONOTIFY tag have received the transmitted
data. A :NOTIFY or :NONOTIFY tag in the nicknames section
overrides this default. The NOTIFY, NOTIFY(ALL) or
NONOTIFY option on the TRANSMIT command overrides any
default in the NAMES data set.
The nicknames section consists of nickname entries which begin
with the :NICK tag. The following tags can be used:
:NICK.nickname
Nicknames can be 1 to 8 alphanumeric characters in length
and are used to begin a new entry in the nicknames section.
:NOTIFY or :NONOTIFY
This tag will override any default set in the control
section but will be overridden if the NOTIFY, NOTIFY(ALL),
or NONOTIFY option of the TRANSMIT command is used.
:NODE.nodeid
This tag specifies a network node name for the nickname
entry.
:USERID.userid
This tag specifies the userid of the user specified in the
:NICK tag. :LIST or :CC may not be used in the same entry
when :USERID is used.
EJECT
:LOG or :NOLOG
This tag will override any default set in the control
section but will be overridden if the LOG or NOLOG option
of the TRANSMIT command is used.
:LOGLST or :NOLOGLST
This tag is used when the nickname entry specifies a
distribution list rather than an individual. It specifies
whether or not a log entry should be made for every
addressee in the list.
:NAME.username
This tag contains a text name of the user or group being
defined in the :NICK entry. This name can be a maximum of
30 characters long and will appear in the copylist and log
entries, if any, for this nickname.
:ADDR.address
This tag specifies the address of the user or group being
defined in the :NICK entry. You must separate individual
address lines by semicolons.
:LIST.name name-list
This tag is used to specify a distribution list of
addressees. The list of names can be either nicknames or
node.userid or the name of another distribution list.
:CC.name name-list
This tag is a synonym to the :LIST tag.
For more information, you may enter the TSO command HELP NICKNAME
or HELP NICKNAME OPERAND(:tagname). You may also refer to the TSO/E
COMMAND LANGUAGE REFERENCE MANUAL - SC28-1134.